XendAPI: After VBD_destroy and VIF_destroy the managed config must be saved

...otherwise already deleted devices appear again in configuration
after a xend restart.

Signed-off-by: Lutz Dube <Lutz.Dube@ts.fujitsu.com>

diff --git a/tools/python/xen/xend/XendAPI.py b/tools/python/xen/xend/XendAPI.py
index 06134ca7ac4193d2b792cfa645c9ea280d4cb374..521ee33beb18325eaa166fcf2cee7ab7fbbbd2e4 100644 (file)
--- a/tools/python/xen/xend/XendAPI.py
+++ b/tools/python/xen/xend/XendAPI.py
@@ -2053,6 +2053,7 @@ class XendAPI(object):
 
         XendTask.log_progress(0, 100, vm.destroy_vbd, vbd_ref)
 
+        xendom.managed_config_save(vm)
         return xen_api_success_void()
 
     def _VBD_get(self, vbd_ref, prop):
@@ -2220,6 +2221,8 @@ class XendAPI(object):
             return xen_api_error(['HANDLE_INVALID', 'VIF', vif_ref])
 
         vm.destroy_vif(vif_ref)
+
+        xendom.managed_config_save(vm)
         return xen_api_success_void()
 
     def _VIF_get(self, ref, prop):